Control system for a remote vehicle

ABSTRACT

Control system for a remote vehicle comprises a twin grip hand-held controller including: a left grip shaped to be held between a left little finger, ring finger, and the ball of the thumb, leaving the left index finger, middle finger, and thumb free; a left control zone adjacent to the left grip, including a first analog joystick and a first 4-way directional control manipulable by the left thumb, and a left rocker control located on a shoulder portion of the controller; a right handed grip shaped to be held between the right little finger, ring finger, and the ball of the thumb, leaving the left index finger, middle finger, and thumb free; and a right control zone adjacent the right grip, including a second analog joystick and a second 4-way directional control manipulable by the right thumb, and a right rocker control located on a shoulder portion of the controller.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to controlling a remote vehicle,and more particularly to an improved system for remotely controlling oneor more vehicles in real time from a dismounted position.

2. Description of Related Art

Improving user experience with remote vehicle interfaces is an ongoingarea of development. Particular areas of concern include optimizingmission-critical response time, minimizing training and logisticssupport, minimizing complexity, attaining an ideal weight, size, andsimplicity while increasing durability and reliability, and the abilityto integrate the control system into gear normally worn or carried bythe user.

Users can be burdened by large amounts of equipment and gear. Forexample, typical military gear includes an Outer Tactical Vest (OTV) andweapons such as an M16 or an M4 carbine. Gear often additionallyincludes one or more of ammunition, first aid kits, hip- or back-worncanteens, gas masks, radios, and/or monocles. Such equipment is commonlystored and carried in or on specific military gear; for example, MOLLEruck sacks (Army) or Improved Load Bearing Equipment (ILBE) AssaultPacks (Marines). The most critical equipment is preferably locatedwithin immediate arms' reach on the front of the torso, typically aroundthe waist. Extensive gear can result in limited range of motion formilitary personnel, complicating fast transitions into various firingpositions as well as entering and exiting vehicles.

Generally, users are willing to carry additional equipment if it addsvalue, but will not wear equipment that interferes with their safety,mobility, or mission effectiveness. Also, users have indicated apreference for Velcro® fasteners over other fasteners such as ALICEclips or the straps associated with the MOLLE system. Further, there isa preference for a minimum number of wires, because wires can get caughton various protrusions, especially when entering and exiting vehicles.Further, military personnel want to be able to take off their helmetsperiodically, and therefore prefer to not be encumbered by anynon-detachable head gear. Still further, military personnel do not wantto be targeted as a specialized soldier (remote vehicle operator) andtherefore value concealable components, particularly when the componentsare not in use.

Users of remote vehicles for detecting and disarming explosive devicesrequire delicate control of grippers and arms of the remote vehicle todisarm explosive devices and gather evidence, but also require a certainamount of strength to maneuver explosive devices to a safe location.

There are a number of remote vehicles that may be deployed, depending onsituational needs. Each remote vehicle may be capable of performing anumber of missions and a variety of tasks. However, many elements ofinteracting with the various remote vehicles are common. It is thereforedesirable to provide a common controller baseline that can be minimallymodified to accommodate a variety of remote vehicles, missions, andtasks. The common baseline should be intuitive to a user and supportdismounted (remote) operations.

Further, situational awareness must only be minimally compromised by theremote vehicle's control system.

SUMMARY OF THE INVENTION

Accordingly, the present invention provides a control system foroperation of a remote vehicle comprises a twin-grip hand-held controllerhaving a volume of less than 1 liter and a weight of less than 1 lb. Thetwin-grip hand-held controller includes: a left grip shaped to be heldbetween a user's left little finger, ring finger, and the ball of thethumb, leaving the user's left index finger, middle finger, and thumbfree; a left control zone adjacent to the left grip, including a firstanalog joystick and a first 4-way directional control manipulable by theleft thumb, and a left rocker control located on a shoulder portion ofthe controller; a right handed grip shaped to be held between the user'sright little finger, ring finger, and the ball of the thumb, leaving theuser's left index finger, middle finger, and thumb free; a right controlzone adjacent the right grip, including a second analog joystick and asecond 4-way directional control manipulable by the right thumb, and aright rocker control located on a shoulder portion of the controller; atether zone between the left control zone and the right control zone,including a tether anchor configured to tether the hand controllerbetween the left grip and the right grip and to permit the handcontroller to hang with the left grip and right grip pointing upward; atether extending from the tether anchor to the right shoulder of anoperator, the tether including a strain relief section; and aquick-release pad to be worn on an operator's chest, the quick-releasepad including a first fastener for affixing the quick-release pad toavailable mounts on the operator, and a second quick-release fastenerfor holding the hand-held controller to the quick-release pad to bereadily removable by pulling on the hand-held controller.

The present invention additionally provides a control system foroperation of remote vehicle having a main drive and a flipper drivearticulated in a pitch plane. The control system comprises a processorcapable of communicating with the remote vehicle and a twin-griphand-held controller for providing commands to the processor. Thetwin-grip hand-held controller includes: a left grip that permits auser's left index finger, left middle finger, and left thumb to operatecontrols; a driving joystick for forward/reverse and left/right steeringof the remote vehicle, and a first array of buttons, the drivingjoystick and the first array of buttons being manipulable by the user'sleft thumb; a camera joystick for controlling a camera pose of theremote vehicle, and a second array of buttons, the camera joystick andthe second array of buttons being manipulable by the user's right thumb;a rocker control for controlling a flipper of the remote vehicle, therocker control being aligned along a pitch plane parallel to thearticulated flipper drive, and controlling a rotational position of aflipper drive; and a brake control that actuates a brake on the remotevehicle.

The brake control may be adjacent to the driving joystick andmanipulable by the user's left thumb, or it may be a dead man's switchlocated under the user's left forefinger, left middle finger, rightforefinger, or right middle finger.

One of the first array of buttons and the second array of buttons mayinclude a speed governor that sets speed ranges for the remote vehicleand/or a button that selects among predetermined poses for the robot.

The twin-grip hand-held controller may alternatively include: a leftgrip that permits a user's left index finger, left middle finger, andleft thumb to operate controls; a driving joystick for forward/reverseand left/right steering of the remote vehicle, and a first array ofbuttons, the driving joystick and the first array of buttons beingmanipulable by the user's left thumb; a camera joystick for controllinga camera pose of the remote vehicle, and a second array of buttons, thecamera joystick and the second array of buttons being manipulable by theuser's right thumb; and a mode button or toggle located under the user'sleft forefinger, right forefinger, left middle finger, or right middlefinger.

The twin-grip hand-held controller may alternatively include: a leftgrip that permits a user's left index finger, left middle finger, andleft thumb to operate controls; a driving joystick for forward/reverseand left/right steering of the remote vehicle, and a first array ofbuttons, the driving joystick and the first array of buttons beingmanipulable by the user's left thumb; a camera joystick for controllinga camera pose of the remote vehicle, and a second array of buttons, thecamera joystick and the second array of buttons being manipulable by theuser's right thumb; and one of a directional pad or a right button arrayfor selecting among one or more predetermined poses of the remotevehicle.

The predetermined poses may include predefined positions of the remotevehicle's flippers and camera or of the remote vehicle's flippers, headand neck. Selection of a predetermined poses may be made with the user'sright thumb. A user interface may illustrate the predetermined posesavailable for selection, and software may be included for transitioningamong the predetermined poses. The software for transitioning among thepredetermined poses may transition the remote vehicle through arbitraryintermediate poses.

The twin-grip hand-held controller may alternatively include: a leftgrip that permits a user's left index finger, left middle finger, andleft thumb to operate controls; a driving joystick for forward/reverseand left/right steering of the remote vehicle, and a first array ofbuttons, the driving joystick and the first array of buttons beingmanipulable by the user's left thumb; a camera joystick for controllinga camera pose of the remote vehicle, and a second array of buttons, thecamera joystick and the second array of buttons being manipulable by theuser's right thumb; and one of a directional pad or a right button arrayfor selecting among one or more autonomous assist behaviors of theremote vehicle.

The autonomous assist behaviors may include at least one of ballisticbehaviors and continuous behaviors. The autonomous assist behaviors mayinclude predefined positions of the remote vehicle's flippers and cameraor predefined positions of the remote vehicle's flippers, head, andneck. Selection of an autonomous assist behavior may be made with theuser's right thumb. A user interface may illustrate the autonomousassist behaviors available for selection, and software may be includedfor controlling the autonomous assist behaviors.

The present invention still further provides a system for controlling aremote vehicle. The system comprises a hand-held controller having aplurality of buttons; a display including a graphical user interfacehaving soft buttons; and a processor in communication with the hand-heldcontroller and the display. Buttons of the hand-held controller aremapped to soft buttons of the graphical user interface to allowactuation of soft buttons of the graphical user interface. The hand-heldcontroller is capable of switching between two or more button functionmodes, wherein each button function mode assigns different functions toone or more of the buttons of the hand-held controller.

The soft buttons of the graphical user interface may allow selection ofone or more autonomous assist behaviors of the remote vehicle. Theautonomous assist behaviors may include predetermined poses that mat beone or more of ballistic and continuous.

The display may be a head-mounted display and the buttons on thedirectional pad of the hand-held controller may be mapped to the softbuttons of the graphical user interface.

Other features and advantages of the present invention will becomeapparent as the following Detailed Description proceeds, and uponreference to the attached figures, and wherein:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a embodiment of a control system of the presentinvention and a remote vehicle;

FIG. 2 is a top view of an embodiment of a hand-held controller of thecontrol system of the present invention;

FIG. 3 is a rear view of the embodiment of FIG. 2;

FIG. 4 is a side view of the embodiment of FIG. 2;

FIG. 5; is a front sectional view of an embodiment of a roller wheel foruse with the control system of the present invention;

FIG. 6 is a side view of the roller wheel embodiment of FIG. 5;

FIG. 7 is a top view of an embodiment of a rotary ring switch for usewith the control system of the present invention;

FIG. 8 is another top view of the rotary ring switch embodiment of FIG.7;

FIG. 9 is a side view of the rotary ring switch embodiment of FIG. 7;

FIG. 10 illustrates an embodiment of a quick-release pad of the controlsystem of the present invention;

FIG. 11 is another embodiment of a user interface of the control systemof the present invention;

FIG. 12 is an embodiment of a user interface of the control system ofthe present invention;

FIG. 13 illustrated an exemplary use of the control system of thepresent invention with a remote vehicle;

FIG. 14 illustrates an exemplary embodiment of custom robot posesactivated using the control system of the present invention;

FIG. 15 illustrates another exemplary embodiment of custom robot posesactivated using the control system of the present invention;

FIG. 16 illustrates initiation of a stair climbing autonomous assistbehavior activated using the control system of the present invention;

FIGS. 17A and 17B illustrate positions of a remote vehicle relative totarget stairs as the remote vehicle ascends or descends the stairs inaccordance with a stair climbing autonomous assist behavior activatedusing the control system of the present invention;

FIG. 18 illustrates an exemplary method for performing a stair climbingbehavior activated using the control system of the present invention;

FIG. 19 illustrates a cruise control routine included within a cruisecontrol autonomous assist behavior activated using the control system ofthe present invention;

FIGS. 20A and 20B illustrate a remote vehicle responding to new headingcommands to change direction in accordance with cruise controlautonomous assist behavior activated using the control system of thepresent invention;

FIG. 21 illustrates a flow chart showing the flow of informationaccording to an embodiment of a cruise control autonomous assistbehavior activated using the control system of the present invention;

FIG. 22 illustrates an embodiment of a routine carried out to generatecruise commands of a cruise control autonomous assist behavior activatedusing the control system of the present invention;

FIG. 23 illustrates an exemplary embodiment of an interaction between acruise control autonomous assist behavior and other behaviors installedon the remote vehicle's on-board computer; and

FIGS. 24A-24D illustrate an embodiment of an interaction between acruise control autonomous assist behavior and an obstacle avoidanceautonomous assist behavior.

DETAILED DESCRIPTION OF THE INVENTION

A control system of the present invention includes an unobtrusive,highly mobile control system that provides the user with a remotevehicle such as a teleoperated remote control vehicle (embodied hereinby a robot) operating experience that seamlessly integrates with theuser's other tasks and duties. Situational awareness is minimallycompromised when operating the system, as it is critical for the user tobe aware of his surroundings. Basic components of the control system,which are illustrated in FIG. 1, include a display, an input device, aprocessor, an antenna/radio (for wireless communication), and software.In an embodiment of the invention, a head-mounted display provides videodisplay from one or more remote vehicle cameras. A hand-held controller,preferably having a twin-grip design, includes controls to drive,manipulate, and monitor the robot and its payloads. Audio mayadditionally be provided via the hand-held controller, the display, ordedicated listening devices such as, for example, Bluetooth headsetscommonly used with mobile phones. In an embodiment of the invention, amicrophone is provided on the hand-held controller, the processor, thedisplay, or separately from these components, and can be used with aspeaker on the remote vehicle to broadcast messages. A button on thehand-held controller or a soft button within the GUI can be used toactivate the speaker and microphone for broadcasting a message.

The system is preferably compatible with MOLLE packs, ALICE packs,ILBEs, or OTVs commonly worn by users. The system preferably has thefollowing additional characteristics: lightweight (e.g., no more than 7pounds total, and no more than 2 pounds for the hand-held controller);mobile; small form factor (e.g., able to integrate with existing usergear); wearable or capable of being carried in a backpack; easy to puton/take off; adequate computer processing power; minimal or no externalcables; meets mission time thresholds (e.g., 5 hours); rugged tointended environment (e.g., temperature, shock, vibration, water, etc.);able to withstand being dropped (e.g., 3 feet).

The platform should have standard interfaces for networking, display,wireless communication, etc.

The control system, as illustrated in FIG. 1, includes a processor suchas a rugged laptop computer. The processor could alternatively be anysuitably powerful processor including, for example, a tablet PC. Theprocessor communicates with the remote vehicle wirelessly or via atether (e.g., a fiber optic cable). Although wireless communication maybe preferable in some situations of remote vehicle use, potential forjamming and blocking wireless communications makes it preferable thatthe control system be adaptable to different communications solutions,in some cases determined by the end user at the time of use. A varietyof radio frequencies (e.g., 802.11), optical fiber, and other types oftether may be used to provide communication between the processor andthe remote vehicle.

The processor must additionally communicate with the hand-heldcontroller and the display. In a preferred embodiment of the invention,the processor is capable of communicating with the hand-held controllerand the display, illustrated in the present embodiment to be ahead-mounted display, either wirelessly or using a tether. To facilitatewireless communication among the various elements of the system, theprocessor includes a radio and an antenna.

It addition, the processor includes software capable of facilitatingcommunication among the system elements, and controlling the remotevehicle. In an embodiment of the invention, the software is aproprietary software and architecture, including a behavioral system andcommon OCU software, which provide a collection of software frameworksthat are integrated to form a basis for robotics development. Accordingto an embodiment of the invention, this software is built on acollection of base tools and the component framework, which provide acommon foundation of domain-independent APIs and methods for creatinginterfaces, building encapsulated, reusable software components,process/module communications, execution monitoring, debugging, dynamicconfiguration and reconfiguration as well as operating system insulationand other low-level software foundations like instrument models, widgetlibraries, and networking code. In an embodiment of the invention, theprocessor performs all of the data processing for the control system.

Referring to FIG. 2, an exemplary embodiment of a twin-grip hand-heldcontroller is illustrated. The hand-held controller includes left andright grips shaped to be held between a little finger, a ring finger,and the ball of a thumb of a respective hand, leaving the index finger,middle finger, and thumb of the respective hand free to manipulatecontrols. Two joysticks (analog, having 4 degrees of freedom) areprovided on the left and right sides of the hand-held controller. Thejoysticks may be 2-axis analog. In an embodiment of the invention,analog-to-digital resolution of the joysticks is at least 12-bit peraxis with the joystick center “dead band” (maximum offset from center onspring return) being less than about 3% of total resolution. If pressed,the joysticks can function as digital buttons. The present inventionalso contemplates using pucks (6 degrees of freedom) instead ofjoysticks.

In an embodiment of the invention, the left joystick is commonly used todrive the remote vehicle (forward, backward, left, and right). The rightjoystick controls one or more other functions of the robot depending ona selected button function mode, including a camera (e.g., the attackcamera), a weapon, or flipper control.

A directional pad is located on a left side of the hand-held controllerand includes an array of four or five discrete digital buttons formanipulation by the user's left thumb. The buttons are arranged in adiamond shape with an optional button in the center. The four buttonsnot in the center preferably come to a rounded point at one end toindicate direction. One button points up, one points down, one pointsright, one points left. In an embodiment, the four buttons not in thecenter have a generally flat exposed surface and the center button has agenerally hemispherical exposed surface and is raised above thesurrounding buttons. In an embodiment of the invention, the directionalpad is used to navigate among the soft buttons of a GUI displayed by thehead-mounted display. The center button of the array, when present, maybe used to select a soft button of the GUI.

A right button array includes an array of four discrete digital buttonsfor manipulation by the user's right thumb. The buttons are arranged ina diamond shape and are circular with exposed surfaces that may be atleast slightly curved. The right button array can be used to control avariety of functions such as camera selection, robot light setting, androbot speed. When no center button is provided on the directional pad,one of the buttons of the right button array may be used to select asoft button of the GUI.

A center button array is shown to include five discrete digital buttonsfor manipulation by the user's thumbs. A first button is generallylocated in an upper left region of the center area, a second button isgenerally located in an upper right region of the center area, a thirdbutton is generally located in a lower left region of the center area, afourth button is generally located in a lower right region of the centerarea, and a fifth button is generally located in the center of the otherbuttons. The first four buttons are elongated (generally rectangular)and the fifth button is generally hemispherical. In an embodiment of theinvention, the center button is larger than the other buttons in thecenter array.

In an embodiment of the invention, the upper right button (second)button is the menu button, which brings up a menu within the GUIdisplayed by the head-mounted display. The menu is preferably ahierarchical menu, such as a drop-down menu, that allows the user toselect a screen layout, a robot to control, select a safe mode for therobot (such as observe mode), manage and play video, audio and snap shotrecordings, select among other settings such as brightness, andtime/date, or review documentation regarding the controller or therobot. In this embodiment, the upper left (first) button acts as a pauseor brake button for the robot, ceasing movement of the robot untilreleased. To prevent accidental activation, the pause/brake button maybe recessed and/or may require a minimum force for activation.

A button on the hand-held controller or a soft button within the GUI canbe used to switch controllers, so that another hand-held controller oralternative control device can take over control of the remote vehicle.This can allow multiple operators to control the same remote vehicle.

The pause or brake button may alternatively be designed as a dead man'sswitch to ensure safe operation of the robot—if the user's finger isreleased from the switch, the robot ceases to operate. In an embodimentof the invention, the dead man's switch is located under the user's leftindex finger, right index finger, left middle finger, or right middlefinger.

Bumper or rocker buttons are located on the shoulders of the hand-heldcontroller, the buttons making up a rocker control. Two rocker buttonsmake up a first rocker control on the left shoulder and are orientedvertically, and two more rocker buttons make up a second rocker controlon the right shoulder and are also oriented vertically. As analternative to rocker buttons, one-axis switches may be provided on theleft and right shoulders (not shown). The rocker buttons, being alignedvertically along the shoulder of the hand-held controller, are therebylocated in a pitch plane parallel to the articulated flipper drive. Inan embodiment of the inventions, the rocker control on the rightshoulder is used for flipper control.

The directional pad, left joystick, and left shoulder rocker controlmake up a left control zone. The right button array, right joystick, andright shoulder rocker control make up a right control zone.

A power button is located between the left and right shoulder areas ofthe hand-held controller. In the illustrated embodiment, the button iscircular with a flat protruding surface. The button may optionally berecessed (to prevent inadvertent actuation) and/or backlit with an LEDthat indicates the state of the hand-held controller (i.e., on or off).In an embodiment of the invention, the area of the hand-held controllerimmediately surrounding the power button is smooth to facilitate usingelectrical tape to cover the power button and its LED as needed.Covering the power button can avoid detection of the hand-heldcontroller. The power button on the hand-held controller may control thestate of just the hand-held controller, or of a number of other systemcomponents, such as the processor and one or more displays (e.g., thehead-mounted display).

An embodiment of the invention includes a tether zone (see FIG. 3)located between the left control zone and the right control zone, whichincludes a tether anchor configured to tether the hand-held controllerbetween the left grip and right grip and permit the hand-held controllerto hang in use (see FIG. 13) with the left grip and right grip pointingupward. A tether, or cord, extends from the tether anchor, preferably tothe right shoulder of a dismounted operator.

In an embodiment of the invention, the tether is detachable from thehand-held controller, and connects the hand-held controller to theprocessor for non-wireless communication between the two. In anembodiment of the invention, the hand-held controller can operate onbattery power and communicates wirelessly with the processor, but hasthe ability to accept a tether when non-wireless connection ispreferred.

In an embodiment of the invention, the tether has a strain reliefallowing it to be flexible but also physically support the weight of thehand-held controller and withstand being dropped the a distance equal tothe tether's length (e.g., 3 feet) without damage or disconnection.

In an embodiment of the invention, the tether attaches to the hand-heldcontroller via an environmentally sealed connector, such as push-pull,screw latching, etc. The same environmentally sealed connection may beused where the tether connects to the processor. The tether connectorsmay be keyed to prevent pin misalignment during connection.

FIGS. 5 and 6 illustrate an optional roller wheel that may be providedon the hand-held controller. In an exemplary embodiment, the rollerwheel is surrounded by a textured tire and sits in a cavity of thehand-held controller. The cavity is formed in the exterior surface ofthe hand-held controller and includes an interior shell to encase theroller wheel. An axle extends between two sides of the interior shelland allows the roller wheel to rotate within the cavity. Bushings mayadditionally be provided to reduce friction and wear. The axle extendsinto a rotary transducer located on at least one side of the cavity, therotary transducer measuring rotation of the roller wheel and convertingit to a digital output. The location of the roller wheel on thehand-held controller, if provided, may vary, although the wheel ispreferable located so that it can be actuated by the user's thumb orforefinger (either left or right). The roller wheel may be used, forexample, for camera zoom or to scroll among soft buttons in the GUI.

FIGS. 7, 8, and 9 illustrate an optional rotary ring switch. In theillustrated exemplary embodiment, the rotary ring switch is locatedaround a joystick and includes three positions on the ring that may beselected by sliding a selector along the ring to one of the positions.In an embodiment of the invention, the rotary ring switch surrounds theleft joystick so that selection is made with the user's left thumb. Therotary ring switch may be used to select among button functions modes.

The present invention contemplates a variety of locations for the ringswitch if one is provided, as well as a varying number of positions forselection. For example, the ring switch could surround the rightjoystick, the directional pad, the right button array, or the centerbutton array.

The present invention contemplates using labels (not shown) on or nearthe buttons of the hand-held controller to indicate the functionality ofone or more of the buttons.

It will be appreciated by those skilled in the art that location andshape of the buttons may vary among embodiments of the invention. Thepresent invention contemplates a variety of button shapes and locations.Additional buttons may be added, or buttons may be removed within thescope and spirit of the invention.

The present invention contemplates additional or alternativefunctionality for the hand-held controller. For example, the hand-heldcontroller may be able to detect aspects of its own movement viaaccelerometers and gyroscopes and translate that movement into remotevehicle control functions such as, for example, scrolling through a GUImenu. While the hand-held controller's movement could be translated intocorresponding movement of the remote vehicle, such control may not beadvisable in certain situations where precise control of the remotevehicle is critical and/or the controller may be subject to unforeseenjostling with potentially hazardous results in terms of correspondingmovement of the remote vehicle.

An embodiment of the invention provides mode changing software forchanging button mapping of the hand-held controller between, forexample, driving a robot, manipulating an arm, controlling a camera,etc.

In an embodiment of the invention, switching among button function modesof the hand-held controller is accomplished by actuating a button ortoggle-type switch, preferably using the operator's index finger(s).This can be accomplished using an above-described rotary ring switch,another button on the hand-held controller, or even the optional rollerwheel described above. The present invention also contemplates switchingbutton function modes on the left side of the controller which oneswitch or button, preferably located on the left side, and switchingbutton function modes on the right side of the controller which anotherswitch or button, preferably located on the right side.

According to an embodiment of the invention, button function modesinclude:

Drive Mode—the left joystick is used to steer the robot forward, back,left, and right, the left button array is used to control the attackcamera (for a robot having, for example, a drive camera and an attackcamera), the right joystick controls a spooler (for example containingfiber optic cable), the right button array controls a variety offunctions such as the camera zoom, robot lights, robot speed, an camerachoice (allows user to choose one or more cameras as, for example,primary and secondary), and the right shoulder is for flipper control.

Manipulate (Gripper) Mode—the left joystick is used to move the gripperforward, back, left, and right, the right joystick is used to move thegripper up and down and to fold or unfold the elbow, and the rightshoulder buttons are used to rotate the gripper clockwise andcounterclockwise.

Target (Attack Camera) Mode—The left joystick is used to move the attackcamera forward, back, left, and right, and the right joystick is used tomove the attack camera up and down.

Joint Mode—The left joystick folds and unfolds the gripper shoulder(e.g., using the top and bottom buttons), and rotates the turretclockwise and counterclockwise (e.g., using the right and left buttons).The right joystick folds and unfolds two gripper elbows. The left buttonarray controls the attack camera, and the right button array controls avariety of functions such as the camera zoom, robot lights, robot speed,and camera choice. The right shoulder buttons are used to rotate thegripper clockwise and counterclockwise.

Menu (GUI Navigation) Mode—The left joystick navigates a cursor up,down, right, and left, the left button array moves the menu itself up,down, left, and right, and the right button array includes cancel andselect functions.

Among the above exemplary button function modes, certain buttons maymaintain the same functions, such as the top left button of the centerbutton array being a pause/brake button, and the top right button of thecenter button array being a menu button. In addition, the button tochange among the above functional modes may remain the same. In anembodiment of the invention, the left joystick is always used to drivethe remote vehicle and the directional pad is always used to navigatesoft buttons of the GUI. It is the other buttons that changefunctionality among modes.

It should be understood that the present invention contemplates avariety of button mapping scenarios, and a variety of single andcombined function modes that allow the operator to control one, two, ormore payloads of the remote vehicle with the same hand-held device bymanipulating the buttons on the hand-held controller.

In an embodiment of the invention, the weight of the hand-heldcontroller, including the cord, is less than or equal to two pounds. Ina preferred embodiment, the weight of the hand-held controller itself isless than one pound, and the dimensions are no larger than4.5″×2.5″×6.5″.

According to an embodiment of the invention, the hand-held controller isruggedized. For example, the casing and switch plate may comprisealuminum, and the unit or parts thereof may be coated in plastisol oranother suitable coating. In addition, the tether connection may beenvironmentally sealed, and the buttons may additionally be madewaterproof as is know to those skilled in the art, particularly in thearea of waterproof cameras.

For adhering the hand-held controller to the user's gear, an embodimentof the invention includes a quick-release system. An embodiment of thequick-release system includes a quick release pad, an embodiment ofwhich is illustrated in FIG. 10. The quick-release pad preferablycomprises Velcro® on an outer-facing side thereof, and has a sizesuitable to allow releasable but stable attachment of the hand-heldcontroller to the pad. The pad is attached to a loop on the user's gear.In the embodiment of FIG. 10, the loop is a horizontal loop such asthose provided on an OTV. A strap connected to the quick-release padcircles through the OTV loop to attach the quick-release pad to the OTV.An additional quick-release mechanism (not shown) may be used toreleasably fasten the tether (which connects the hand-held controller tothe processor) to the user's gear. Complementary material is located onan underside the hand-held controller to mate with the quick-releasepad. In an embodiment of the hand-held controller including protrusionsextending from a bottom thereof (see FIGS. 3 and 4), the complementarymaterial is located on the protrusions. In an alternate embodiment with,for example, a flat bottom, at least a portion of the bottom wouldinclude complementary material. Because Velcro® can wear out and becomeless effective, the present invention contemplates the Velcro in thequick-release system being easily replaceable.

The head-mounted display illustrated in FIG. 1 generally indicates adisplay device worn on a user's head or as part of a helmet, which has adisplay optic in front of one or both eyes. A typical head-mounteddisplay has one or two displays with lenses and semi-transparent mirrorsembedded in a helmet, eye-glasses, or a visor. The display units areminiaturized and may include cathode-ray tubes (CRTs), liquid crystaldisplay (LCD), Liquid Crystal on Silicon (LCos), or an organiclight-emitting diode (OLED).

The head-mounted display allows the remote vehicle operator to see whatthe remote vehicle sees through one or more cameras, so that the remotevehicle can be controlled when it is not within the operator's line ofsight, and also allows the operator to maintain situational awareness.In an embodiment of the invention, the head-mounted display is an Icuititactical display.

The head-mounted display displays a GUI with views from the robot'scamera(s) and information about the robot such as battery life,payloads, communication status, etc., and also displays soft buttonsthat are mapped to the hand-held controller buttons and allow the userto more intuitively control the robot using the hand-held controller.

The present invention contemplates using one or more head-mounteddisplays with a single control system. In addition, the video streamfrom the robot camera(s) can be multi-casted for use by multipleclients. Indeed, the multiple clients need not only be multiplehead-mounted displays, but may alternatively or additionally include avariety of displays and/or recoding devices in a variety of locations.

The head-mounted display is preferably capable of either wireless ortethered communication with the hand-held controller through theprocessor.

As stated above, a menu mode of the hand-held controller allows the userto navigate among soft buttons or icons displayed by the head-mounteddisplay. Exemplary embodiments of the GUI display are illustrated inFIGS. 11 and 12.

As illustrated in the embodiment FIG. 11, the head-mounted displayprovides the user with a variety of information in what is indicated asa “max camera” layout. In this illustrated embodiment, the main image isa video stream from the robot's attack camera and the smaller image inthe lower right corner is video stream from the robot's drive camera. Asan alternative to video streams, a series of snapshots can be displayedat predetermined time intervals. The status of the attack camera (e.g.,front zoom) is displayed in the upper left corner, and certain cameracontrol icons or soft buttons are presented under the camera status. Inthis embodiment, the icons include zoom in, zoom out, IR filter on/off,IR light off/low/medium/high, camera default position (designated inthis embodiment as a V in a sun shape), camera setting choices, audiochoices, snap shot, and video record on/off. In this embodiment, uponchoosing (by pressing the soft button or icon by manipulating thehand-held controller in the menu mode) camera settings and audio, theGUI pops up a screen to select among a variety of setting options. In anembodiment of the invention, the icons can be minimized. Above thestatus of the camera, the robot's name can be displayed (illustratedherein as “Name567890123456.”

The camera may be returned to its default position, or otherwisecontrolled, via the soft button mentioned above, or a button on thehand-held controller.

Additional icons or soft buttons may be displayed, for example on theright side of the head-mounted display view. In this embodiment, theicons or soft buttons include, from top to bottom, status ofcommunication link (with robot), battery charge level (of the robot andthe OCU), speed toggle (wherein the snail icon indicates that the robotis in a slow range of speed within the available scalable range ofspeed), robot heading, two icons indicating the robot's position andheading, and a variety of autonomous assist options such as predefinedposes (described in detail below).

Another embodiment of the system's GUI, indicated as a “quad” layout, isillustrated in FIG. 12. The larger, upper left image is a video streamfrom the robot's attack camera and the smaller image in the center ofthe display is video stream from the robot's drive camera. As analternative to video streams, a series of snapshots can be displayed atpredetermined time intervals. The status of the attack camera (e.g.,front zoom) is displayed in the upper left corner, and certain cameracontrol icons or soft buttons are presented under the camera status, asset forth for the prior embodiment. In an embodiment of the invention,the icons can be minimized. Above the status of the camera, the robot'sname can be displayed (illustrated herein as “Name567890123456.” Underthe camera controls is a map icon allowing the user to select additionalinformation from the system's mapping function. To the right of the mapicon and under the video stream from the attack camera, mappinginformation regarding one or more of the robot's prior mission movementscan be displayed. Alternatively, the missions of a number of nearbyrobots are displayed.

Additional icons or soft buttons may be displayed, for example on theright side of the head-mounted display layout. Similar to the previousembodiment, the icons or soft buttons include, from top to bottom,status of the communication link (with robot), battery charge level (ofOCU), speed toggle wherein the snail icon indicates that the robot is ina slow range of speed (within the available scalable range of speed),and a variety of autonomous assist options such as predefined poses. Inthis embodiment, the poses are indicated by name rather that a graphicalrepresentation of the pose itself. Payload icons under the pose iconsallow the user to activate a payload or bring up a control menu for thatpayload. They can also display information regarding selected payloads.Possible payloads include cameras, chemical detection devices, sniperdetection devices, cable spools, batteries, etc. In the illustratedembodiment, payload 3 is an Explorer extension added to the chassis ofthe robot, and payloads 4 and 5 are batteries.

To the right of the video stream from the robot's attack camera is arepresentation of the robot's position and heading, including any tilt.Under the positional representation is an identification of the payloadsand information regarding the payloads, such as an indication ofremaining battery life.

In accordance with the present invention, the user may choose among avariety of GUI layouts, such as the “max camera” and “quad” layoutsdescribed above.

In the above illustrative embodiments of the GUI, the icons or softbuttons may be displayed continuously for the user, who navigates amongthem using a dedicated set of buttons on the hand-held controller (e.g.,the directional pad), or may be displayed only when the hand-heldcontroller is in a menu mode. Additional soft icons or buttons may bedisplayed as desirable. In an embodiment of the invention, theillustrated icons are displayed continuously for the user, and selectionof a menu mode on the hand-held controller brings up an additionalhierarchical menu of functions through which the user can navigate, forexample, using the directional pad.

In an embodiment of the control system of the present invention, audiois provided on one or more of the processor, the hand-held controller,the head-mounted display, or a separate headset.

The control system of the present invention preferably has two states(on and off) and three modes: (1) training mode; (2) operation mode; and(3) maintenance mode. The modes of the control system are distinct fromthe button function modes of the hand-held controller. After beingpowered on, the system may default into an operation mode, default tothe last mode selected, or may initially prompt the user to choose amongthe three modes. Most system functions, including the exemplaryfunctions listed in the table below, are preferably performed in allthree modes.

Power On/off status Communicate communicate with robot status ofcommunications tethered and wireless communication Control drive/stopbrake engage/release speed control flipper control head/neck controlpose selection camera selection camera zoom camera control optionsincluding aperture/exposure/resolution/black and white/color/etc.microphone control on/off/speak speaker control on/off/volume requestinformation/status/data illumination on/off/other select options selectrobot payload control map controls (autonomous robots or assistance)autonomy controls Display display video display health and status(system) display options GPS location/navigational information Audioemit send adjustment options Process process data/audio/video

The system is intended for use by a dismounted operator, dismountedmeans that the operator is freely moving about outside of the remotevehicle(s). However, the system may additionally be used by an operatorthat is not dismounted. The system of the present invention may beuseful to an operator that is not dismounted in an instance where theoperator has difficulty reaching all of the controls needed to operatethe vehicle and its payloads, or the vehicle and other remote vehicles.

The system of the present invention should be capable of controllingremote vehicle mobility, executing operator tasks with one or moreremote vehicles, and supporting maintenance functions.

FIG. 13 illustrates a soldier using the control system of the presentinvention to control a robot. Although the robot is illustrated to be inthe soldier's line of sight, the present invention is directed tonon-line-of-sight operation as well, with the solder using thehead-mounted display to see what the robot sees and thereby effectivelycontrol the robot.

FIG. 13A illustrates an embodiment of the invention including atwo-piece hand-held controller that functions substantially similar tothe one-piece hand-held controller described above. This embodiment ofthe invention allows the left portion of the controller to be attachedto the user's gun, so that one hand can remain on the gun whilecontrolling the remote vehicle.

FIGS. 13B and 13C illustrate another embodiment of the inventionincluding a two-piece hand-held controller. In this embodiment, theright hand controller is mounted to the gun and the left hand controllercan be secured to a quick-release pad. The left hand controller wouldpreferably hang from the user's left shoulder. This embodiment would bepreferably where a user is trained to or tends to keep his firing handon the gun.

The controller may have a variety of shapes and sizes to facilitate easeof gripping and actuation by a user. For example, the one or both piecesof the controller may include a grip portion shaped to be held between alittle finger, a ring finger, and the ball of a thumb of a respectivehand, leaving the index finger, middle finger, and thumb of therespective hand free to manipulate controls. One or both pieces of thecontroller may include a joystick t be manipulated by the user's thumb.The two-piece hand-held controller may include the same number ofbuttons as the one-piece controller above, or may include a more limitednumber of buttons. In an embodiment of the two-piece hand-heldcontroller, the two pieces may be mated to form a one-piece hand-heldcontroller for use as described above. In this embodiment, the twopieces may look more like halves of the one-piece hand-held controllerillustrated in FIG. 2.

As in the prior disclosed embodiments, the hand-held controllercommunicates with the display via a processor (not shown).

Custom Robot Poses (as Represented by GUI Icons)

As shown in FIGS. 14 and 15, once a preconfigured pose available via aGUI, button, or other selection device has been selected, the robot mustmove some or all of its flippers, neck, head with respect to the robotmain body and main drive in order to move from the present pose to thepreconfigured pose (e.g., prairie dog P16, stowed P10, driving on a flatsurface P14, driving on a bumpy or angled surface P20, stair climbing).Some robot configurations may use symmetric flipper arm and body (eachthe same size), providing alternative poses (e.g., inverted Y in whichthe body and/or head is positioned directly above a steepled symmetricflipper and body, inverted arrow in which body and/or head arepositioned above V-oriented symmetric flipper and body—which may furtherrequire inverted pendulum gyroscopic balancing. Only a few exemplaryposes are shown in FIGS. 14 and 15. As discussed here, actions by therobot cause the actuators of the robot to be driven under motor controland amplification as directed by the controller circuit on the robotitself.

Changing or returning to a preconfigured pose from any arbitrary posemay require determining the current position and orientation of therobot's body, drive or flipper arms, neck, and/or head. In an embodimentof the invention, the robot's movement is determined through the use ofmotor encoders (relative or absolute). In an embodiment, the robot'scamera is mounted at a controllable height above the robot's body, andis controlled by the movement of the neck. At the top of the neck, apan/tilt head with camera is mounted. The neck may contain a physicalneck index switch that allows the system to reset the neck location inan absolute sense as the neck's movement passes through a specifiedlocation. By using the starting angle of the neck and motor encoders,the angular location of the neck at any given time can be calculated.Likewise, the pan and tilt position of the head camera can be calculatedusing the start locations. Alternatively, one or more of the flipper armangle, neck angle, head angle (tilt) and head turn (pan) may useabsolute encoders.

By using the current locations of each of the robot elements (body,flipper arm, neck, head pan, and tilt) via motor encoders or otherproprioceptive sensing, the static geometry of the robot itself (forexample, the length of the neck and its arc of travel, the distance fromthe center of rotation to the base of the neck, etc., as well as knownx, y, z locations of the center of mass of each of the body, flipperarms, neck, head), and on-board orientation sensors in any robot element(accelerometers; tilt sensors; gyroscopes; and/or horizon detection), itis possible to produce a frame of reference for each robot element. Inthis case, each frame of reference is represented by a matrix giving thex, y, z location of the robot element and the rotation vectors forforward, left and up.

In an embodiment of the invention, a similar frame of reference can becreated for each element using well-known Denavit-Hartenberg Parametercomputations, e.g., going from the robot base toward the head and cameralocation. For example, the frame of reference for the neck can becomputed using the body frame of reference, Denavit-HartenbergParameters describing the neck geometry, and the current neck angle ofrotation. Using these three inputs, one can compute a new frame ofreference for the neck. Similarly, the pan frame of reference iscalculated, and then the tilt frame of reference is calculated. Becausethe camera is attached to the head, the frame of reference for the headis the frame of reference for the camera itself.

Such calculations from sensor data, performed on the robot itself,permit the robot's starting state to be determined, e.g., including therobot's location and vector (frame of reference) and the camera'slocation and vector (frame of reference). Note that not all of these arenecessary—for a particularly robust robot, only the elementconfigurations as expressed by the relative position of the body,flipper arms, neck, and head may be sufficient.

In the exemplary embodiment illustrated in FIG. 14, one technique ofmoving between positions is to map necessary states betweenpreconfigured poses and current states, including necessary states P24.This state diagram shows that for some robot configurations, a loopamong the states is not necessarily formed, and the path betweenintervening states may be limited to passing through particularsequences of intervening states. For example, as shown in FIG. 14, arobot in stowed pose P10 (solid lines indicating a preconfigured pose),with head and neck retracted and flippers aligned along the main tracks,may be placed in any of three exemplary preconfigured poses (prairie dogP16, bumpy travel P20, and flat travel P14).

In order to move to prairie dog pose P16, in which the robot is stablyelevated on the flipper tracks with the neck elevated to a substantiallymaximum height, the robot must begin by lifting its body, turning itsflipper tracks counterclockwise F-CCW (from the side shown in FIG. 14).It should be noted that there is no way for the robot to enter prairiedog pose by turning the flippers clockwise, as—given a realistic amountof mass in the robot body and center of gravity substantially toward theflipper end of the body—such turning will not tip up the robot body atthe distal end but will only move the robot between flat and bulldogstates (P22 intervening states). As the robot moves through intervening(not selectable via GUI or controller) poses P12, the center ofmass/gravity of each of the body, neck, and head are maintained abovethe midpoint of the flipper arms. As shown in FIG. 14, this may be byspecifying predetermined intervening states and actuations for the robotto pass through. For example, where “CW” is clockwise from the sideshown in FIG. 14 and “CCW” is counter clockwise, first arranging thebody and head above the arms by moving the body only via the flippersF-CCW, then by elevating the neck N-CCW and head H-CW, then by unfoldingall at once vertically flipper F-CCW, neck N-CCW, and head H-CW. Notethat there is no position past the prairie dog pose P16, and furtherrotation will cause the robot to fall over—an optional motion, and onewhich that can be specified as a preconfigured pose that the robot canbe directed to or return from, e.g., stowed-upside-down.

In order to move back to the stowed position P10, or as shown in FIG. 14to move to either of the driving positions P20 or P14, the robot movesback through the necessary states in the opposite order and with theopposite CW or CCW motions.

In order to move to, e.g., bumpy driving pose P20, in which the robot isstably positioned to be driven at slower speeds on the main tracks withthe flipper tracks up to handle small obstacles, the neck and headpositioned rear of the main body to provide a driving view but maximumstatic stability, the robot must begin by turning the flipper tracksclockwise F-CW (from the side shown in FIG. 14). It should be noted thatthere is no way for the robot to enter the driving poses (P20, P14) byturning the flippers counterclockwise, as such turning will tip up therobot body at the distal end and eventually flip the robot (e.g., viathe P20 intervening states). As the robot moves through intervening (notselectable via GUI or controller) poses P22, the flipper arms move to aready-for-driving (or climbing) position. As shown in FIG. 14, this maybe by specifying predetermined intervening states and actuations for therobot to pass through (e.g., first arranging the flipper by moving onlythe flippers F-CW, then by elevating the neck N-CCW and head H-CW).

In order to move to, e.g., flat driving pose P14, in which the robot isstably positioned to be driven at higher speeds on the main tracks withthe flipper tracks also in contact with the ground, the neck and headare positioned at the rear of the main body to provide a driving viewbut maximum moment about the leading end to resist flipping forward uponsudden stops or braking, the robot continues from the bumpy driving poseP20 by moving the flippers F-CW, elevating the neck N-CCW and tiltingthe head H-CW (from the side shown in FIG. 14). In order to “return” toany of the previous preconfigured poses, the robot must pass through theintervening preconfigured poses and intermediate poses.

As discussed, FIG. 14 demonstrates a model in which intervening andintermediate poses are predefined states on a closed, not necessarilylooping, state map, in order to ensure that the robot does not tip over,self collide, or inappropriately lose balance or pose in transitioningfrom a present pose to a preconfigured pose. This is a methodical, butless flexible, approach than having the robot actively maintain balanceusing proprioception, tilt, acceleration, and rotation (gyro) sensors.

FIG. 15 shows a model in which the robot, although passing throughsimilar states, constantly monitors balance proprioception (positionencoders), tilt, acceleration, and/or rotation (gyro) sensors. Thissystem may deal more successfully with uneven ground (shown in FIG. 15)than a system using predefined positions. As shown in FIG. 15, a roboton level, tilted, or uneven ground in the stowed position P30 may bemoved into any of the prairie dog pose (on uneven ground P32), flatdriving pose (on uneven ground P34), and bumpy driving pose P36 bymonitoring position encoding, calculating the overall center of gravityof the robot over that portion of the robot in contact with the ground(either the main body, the main body and flipper tracks, or flippertracks alone), maintaining the individual centers of gravity of thebody, flipper arms, neck, and head in positions over stable center ofground contact, and monitoring and/or controlling acceleration andmovement of the elements to obtain relative tilt, orientation toterrestrial gravity, and/or static and/or dynamic stability. As shown inFIG. 15, because the preconfigured poses are reached by activemonitoring and control of balance, the robot need not pass through allpreconfigured intermediate pose states, but will pass through arbitrary,yet stable and balanced poses P40 on its way from one pose to another(e.g., from bumpy driving P36 to prairie dog P32 without passing throughthe stowed configuration P30). As such, the state map P38 will permitdirect transition from one preconfigured pose state to another through acontinuously changing, but continuously balanced pose transition, andfrom arbitrary current poses P42 directly to preconfigured poses P30 viaa continuously changing, but continuously balanced pose transition(alternatively, a succession of continuously balanced pose transitions).The robot may also seek preconfigured poses by moving only from apresent position into a confined solution space of next positions thatincludes only balanced poses.

It should be further noted that the robot can be controlled to activelyreturn to the preconfigured pose set when disturbed via the continuouslybalanced pose transition, including a self-righting routine interveningbefore the robot seeks the last set preconfigured pose. For example, ifthe robot is temporarily forced into a different pose, or is tipped overor otherwise disturbed, using tilt sensors, proprioceptive encoders,accelerometers, and/or gyro sensors, it may detect this and initiateseeking of the predetermined pose.

Other Autonomous Assist Functions

Autonomous assist functions, in an embodiment of the invention, resideon the robotic platform in memory, and are executed by the robot'son-board computers. Examples of at least two types of behaviors aredescribed herein: Ballistic and Persistent/Continuous.

Ballistic Behaviors—Stair Climbing

The stair climbing behavior is an example of ballistic(operator-initiated) behavior that drives the robot to traverse a set ofstairs in an autonomous manner, after receiving a command to initiatethe behavior and information indicating the location of the stairs fromthe operator. The robot may include a pitch/roll sensor that indicateswhether the robot is tilted relative to the ground, which is used by thestair climbing behavior to decide whether the robot should continueclimbing the stairs.

As an advantage, the robot can be positioned in the vicinity of astaircase and the operator may initiate the autonomous stair climbingbehavior by simply identifying the location of the stairs and inputtinga command to activate the stair climbing behavior. The robot can thenascend or descend the stairs without requiring further input from theoperator.

Referring to FIG. 16, a stair climbing behavior is initiated when theoperator navigates the robot to within a threshold distance of thestairs, such that the stairs are visible in the image displayed both inthe drive camera window 261 and the attack camera window 262. Theoperator then positions a first selector 267 so as to enclose or abut aregion of the window 261 corresponding to the stairs, and similarlypositions a second selector 266 onto a region of the attach camerawindow 262 that also corresponds to the stairs. The control system ofthe present invention contemplates initiating a stair climbing behaviorusing the above-described GUI and soft buttons mapped to buttons on thehand-held controller.

When the target stairs 920 are identified by the first and secondselectors 267, 266, respectively, the operator can then trigger thestair climbing behavior by clicking an on-screen icon as shown in thewindow 252, a button on the hand-held controller, or otherwise inputtinga command that causes transmission of a control signal that activatesthe stair climbing behavior. In accordance with another embodiment, theoperator further inputs whether the robot should climb up the stairs ordescend the stairs. In yet another embodiment, the robot includes aroutine for autonomously determining whether the target stairs 920 areascending or descending relative to the robot, and informs the stairclimbing behavior accordingly.

FIGS. 17A and 17B illustrate positions of the robot relative to thetarget stairs 920 as the mobile robot ascends or descends the stairs 920in accordance with the stair climbing behavior. The robot may initiallyextend its flippers 115 to a predetermined angle (e.g., angle 77 in FIG.17B), in order to facilitate the stair climbing operation. As anexample, FIG. 17A shows the flippers 115 rotated out to about a 180degree angle relative to the main treads 110, to ensure contact with thestairs 920 and to raise the front end of the robot up onto the stairs920. When descending, the robot may instead extend the flippers to anangle 77 that is approximately 45 degrees relative to the main treads110 (see FIG. 17B).

When a tilt sensor on the robot indicates that the angle of tilt of therobot is zero relative to the horizon, the stair climbing behavior maystop and navigation authority may be resumed by another routine.

FIG. 18 shows an exemplary method for performing the stair climbingbehavior. At step 2901 the behavior initializes internal variables (suchas by setting the initial turn rate and roll rate to zero, for example),then determines at step 2902 whether the robot should ascend the stairs.If so, the mobile robot positions the flippers 115 to the appropriateangle for ascending the stairs 920 at step 2903, outputs a speed valuefor ascending the stairs 920 at step 2904; and proceeds to traverse thestairs 920 for one cycle at step 2907. In an embodiment of theinvention, the robot may ascend the stairs at a predetermined speedwhile under control of the stair climbing behavior, such as 0.2 metersper second.

If instead the robot is determined at step 2902 not to be intended toascend the stairs 920, then the behavior positions the flippers 115 toan angle appropriate for descending the stairs 920, sets a speedappropriate for descending stairs, and proceeds to navigate the stairs920 for a cycle at step 2907. Thereafter, the behavior may optionallyperform steps to maintain the robot's alignment with the stairs (inorder not to inadvertently fall off the side of unprotected stairs, forexample) at step 2908, and then determines at step 2909 whether the tiltsensor indicates the existence of tilt.

If tilt exists, the behavior continues to ascend the stairs 920autonomously by returning to step 2907. Otherwise, step 2910 stops therobot from proceeding further, and returns the flippers 115 from theascending or descending position back to the neutral, undeployedposition at step 2911.

In an embodiment of the invention, in order to ascertain whether thereare additional stairs to traverse, the stair climbing behavior may use amedian pitch filter routine to integrate tilt sensing information frommultiple sources, and to reduce false positive determinations of beinglevel. The median pitch filter routine can track pitch information fromthe tilt sensor and use only those values that fall within the median ofall previously recorded values. Accordingly, the routine can reduce thedetrimental impact of transient values on the determination of whetherthe stair traversal is complete.

In accordance with an embodiment of the invention, the median pitchfilter routine stores native pitch/roll sensor output into memory. Anon-board timer then increments and the routine periodically checkswhether it has been incremented by a full half second. If so, then theroutine moves on to the next step; otherwise, the routine stores thetilt sensor output, and increments the timer.

The median pitch filter routine then examines the pitch/roll sensornative output over the full half second and determines the respectivehighest and lowest frequencies of the signal. Using this information,the median pitch filter routine then calculates the median frequency.The median pitch filter routine outputs this calculated median frequencyas the pitch/roll sensor output to the robot's control assembly.

The maintain alignment routine may be used by the stair climbingbehavior to keep the robot moving in a consistent direction with respectto the vertical axis of movement, and allows the robot to ascend ordescend stairs with a turn rate magnitude of zero.

While moving forward with a zero turn rate, for example, the routinesimultaneously samples the roll angle as determined by the pitch/rollsensor output and subsequently calculates a turn rate magnitude from theoutput

In an embodiment of the invention, the equation by which the turn ratemagnitude is calculated may be approximately k*X degrees per second, inwhich k is a constant having a value within the range of 1/10 to 3 and Xrepresents the roll angle. Other embodiments may either use differingformulas.

At one step, the routine checks the roll angle to determine whether itis a value other than zero. If so, then the routine returns to the firststep and moves forward with a roll angle of zero. Otherwise, the routinere-aligns the robot by turning the robot by the calculated turn ratemagnitude. Once the robot is re-aligned, the process goes back to thefirst step and continues to climb forward with a roll angle of zero.

This embodiment of stair climbing behavior, which utilizes a tiltsensor, allows the robot to position itself without the need for walls.Alternatives include the use of a SICK LIDAR sensor to detect walls toposition the robot as the robot moves up the stairs. Other alternativesinclude the use of SONAR to detect walls and position the robot as itmoves up the stairs. Further alternatives include a fully autonomousversion of stair climbing that is implemented upon the detection ofstairs. Such a version may include a sensor placed towards the outer rimof the robot's lower chassis to detect negative obstacles such asdownward stairs, or may require multiple sensors to indicate that thereis an obstacle within the allowed height, meaning that software routineswithin the robot would associate certain dimensions with stairs. Stillother alternatives include a routine that commands the robot tore-position its arms to 180 degrees when it reaches the top of thestairs, or a robot that utilizes a magnetic compass or IMU in additionto or in lieu of a tilt sensor.

Other possible ballistic autonomous assist behaviors include, forexample, preset action sequences, autonomous flipper behavior thatallows an operator to operate the robot manually while the flippers arein an autonomous mode due, perhaps, to difficult terrain conditions,retro-traverse to autonomously navigate the robot back along a returnpath, speed boost, and quick brake.

Persistent Autonomous Behaviors—Cruise Control

The cruise control behavior receives information from the operatorregarding an intended constant speed and heading for the robot. Theinformation sent by the operator typically includes an accelerationvalue and a rotational velocity, both of which are used by the robot todetermine a drive velocity and heading. Preferably, the operator woulduse a left and right puck or joystick included on the hand-heldcontroller to control the robot's movement. In an embodiment of theinvention, the left puck controls the cruise control behavior such thatwhen the left puck is actuated, the cruise control behavior commences,and when the right puck is actuated, the cruise control behavior halts.Alternatively, the cruise control behavior could commence following theactuation of an icon, button, or other actuator located on the hand-heldcontroller.

In an embodiment of the invention employing a puck for cruise control,each puck may have the ability to rotate about a vertical axis,translate forward and backward about a horizontal axis and further tiltaway from the vertical axis. Furthermore, when the puck is translated,rotated or tilted; it is preferable that such movements correspond todifferent movements of the robot. In particular, driving the robot in aforward or backward direction is preferably controlled by thetranslation of the puck about a horizontal axis, alteration of therobot's heading is controlled by the rotation of the puck about avertical axis, and actuation of the flippers included on the robot arecontrolled by tilting the pucks. A particular example of the movement ofthe robot in response to the movement of a puck, is one in which thepuck is rotated about the vertical axis 30° in a clockwise direction,and the puck is moved forward a distance of one-half inch. In response,a robot at rest will adjust its heading by turning 30° in a clockwisedirection, and driving forward at a velocity equivalent to apre-determined value associated with movement of the puck one-half inch.Should the puck be tilted to the right 15° from the normal, the robot'sflippers could respond by rotating towards the ground an angleequivalent to 15°.

FIG. 19 illustrates a cruise control routine 3200 included within thecruise control behavior. When in control of its corresponding actuators,the cruise control behavior executes the cruise control routine 3200which commences by scanning for a new set of cruise commands 3212 fromthe control system, also referred to as the operator control unit 20.Should the routine sense a new set of cruise commands, the routine willthen input these commands as an absolute heading 3215. Since there isoften a time lag between when the robot's cameras record videoinformation and the time that such information is displayed to theoperator, a situation can arise when the robot is moving at a particularspeed and particular heading, and a new heading and/or speed is chosenby the operator and sent to the robot. In such a situation, the robotwill have moved a certain distance during the time between when therobot's camera detected the image, and the image is displayed to theoperator. The latency of the system can cause discrepancies when sendingthe robot cruise commands. To eliminate these discrepancies, in anembodiment of the invention, the operator sends the robot an absoluteheading and velocity. When the robot receives the absolute heading andvelocity, the robot then calculates its new heading and velocity usingthe absolute heading and velocity and the positional and velocity valuesat the time the robot's camera detected the image, rather than thecurrent real-time positional and velocity values. Upon calculating thenew travel velocity and heading, the robot uses real-time positional andvelocity values to calculate a new travel vector 3218.

Once a travel vector 3218 is calculated, the robot will then drive atthe specified velocity and using the specified heading 3201. Whiledriving, the cruise routine gathers real-time positional and velocityvalues from sensors 3203 and compares these values to the chosen travelvector 3206. Should there be a significant difference between thecurrent travel vector and the chosen travel vector, the routineinstructs the robot to adjust its heading and velocity 3221 using pastodometry values. If there is less than a predetermined differencebetween the current travel vector and the chosen travel vector, theroutine will instruct the robot to continue driving 3201. Furtherillustrative of the robot's implementation of cruise control, FIGS. 20Aand 20B display a robot 3444 that responds to new heading commands tochange direction. The robot 3444 moves forward in a particular direction3440. Once the operator control unit 20 retrieves video feedback of therobot's position, the robot's position has changed from its position atthe time the video information was captured 3446 to its current position3244. Thus, the robot has continued along its current path 3440 duringthe time between when the robot collects video information of itsposition at that time 3446 and the time when the robot receives newheading commands from the operator control unit 20. When the operatorcontrol unit 20 sends the heading information to the robot 10, theheading information 3442 is relative to the robot's previous position3446. FIG. 20B displays how the robot uses the heading 3442 generated inrelation to the robot's previous position 3446 to determine a newheading 3452 calculated in relation to the robot's current position3444.

FIG. 21 illustrates an example flow of information in the cruise controlbehavior. Input from the operator control unit is received and processedto produce an updated current intended heading and speed θ_(n), ν_(n).In the equations displayed, θ_(n-1) is the intended heading of thepreceding cycle, t_(n) is the time of the current cycle, t_(n-1) is thetime of the preceding cycle, θ(t_(n)-t_(n1)) is the angular differencebetween the heading of the current cycle and the heading of thepreceding cycle, ν_(n-1) is the intended speed of the preceding cycle,and a (t_(n)-t_(n-1)) is the difference between the speed of the currentcycle and the speed of the preceding cycle.

Simultaneously, input from position reckoning systems (e.g., a compass,IMU, and/or GPS system) is fed to a motion tracking system, whichupdates the reckoned actual heading and speed. The reckoned actual speedand heading of the robot, as well as the updated intended heading andspeed, are passed to a comparator, which generates an appropriate output(such as turn rate and drive motor current) to control the drive system.

FIG. 22 illustrates the routine carried out to generate cruise commands.The routine scans a puck designated for activating and controlling thecruise control behavior 3251, should the routine detect a change in theposition of the puck 3253, the routine will then verify if the changeincluded a rotation of the puck about a vertical axis 3256, otherwisethe routine will continue to scan the puck's position. If the changeincluded a rotation of the puck about a vertical axis 3256, then theroutine will calculate a rotational velocity proportional to therotation of the puck and indicative of the direction the puck wasrotated 3259, and send the new drive heading to the robot 10 where theheading is relayed to the cruise control behavior. Thereafter, theroutine determines whether or not the puck was translated about ahorizontal axis 3265. If so, the routine will then calculate anacceleration/deceleration command 3268 representative of the puck'smovement and send the acceleration/deceleration command 3271 to therobot for relay to the cruise control behavior. Should the routinedetect a tilting of the puck 3274, the routine will exit 3277 becausesuch a movement of the puck indicates flipper movement which iscontrolled by a behavior other than the cruise control and so activationof another behavior causes cruise control to halt. If the routine doesnot detect a tilting of the puck 3274, the routine will then continue toscan the puck's position 3251.

FIG. 23 illustrates an exemplary embodiment of the interaction betweenthe cruise control behavior and the other behaviors installed on therobot's single board computer. When the cruise control behavior hascontrol of the robot's actuators, it executes its cruise routine 3301.However, when the coordinator indicates that another behavior has beenactivated 3303 and that behavior has a higher priority 3306 than thecruise control behavior, it is likely that the cruise behavior will behalted and the cruise routine exited 3318. Otherwise, if the coordinatordoes not indicate that another behavior has been activated 3303, or if abehavior has been activated but that behavior does not have a priority3306 greater than the cruise control behavior; then the cruise routinewill continue to execute 3301. When a behavior with a higher prioritythan cruise control is activated, the coordinator the cruise controlbehavior checks whether this behavior is the obstacle avoidance behavior3309, and if true, allows the obstacle avoidance behavior to havecontrol of the actuators. Otherwise, if the obstacle avoidance behavioris not identified and the behavior has a higher priority than the cruisecontrol behavior, the cruise control behavior will exit the cruiseroutine and halt 3318. Should the obstacle avoidance behavior gaincontrol of the actuators, an obstacle avoidable routine will then beexecuted 3312 by the obstacle avoidance behavior. Once the obstacleavoidance behavior is executed and exited, the obstacle avoidancebehavior will then allow cruise control to have control of the actuators3321. Once in control of the actuators, the cruise control will pick upwhere it left off and begin executing the cruise routine 3301. Withinthe cruise routine 3200, a check is made of the robot's real-time travelvector 3203. Since the obstacle avoidance routine caused the robot toveer away from the chosen travel vector, cruise routine will detect thechange in travel vector and correct the robot's heading and velocity3221 using past odometry values and so that the robot returns to thechosen travel vector.

An embodiment of the invention illustrating the interaction between thecruise control behavior and the obstacle avoidance behavior is displayedin FIGS. 24A-24D. FIG. 24A displays movement of the robot 3458 along thechosen travel vector 3456 dictated by the cruise control behavior, wherethe vector 3456 points the robot toward an obstacle 3454. FIG. 24Billustrates the robot's response to the obstacle 3454 by commanding therobot to drive to a position 3460 within the environment not includedwithin the chosen travel vector, which position 3460 is the result of anavoidance travel vector 3462 instituted by the obstacle avoidancebehavior to cause the robot 10 to avoid the obstacle 3454.

Once the obstacle 3454 is avoided, the cruise control behavior resumescontrol and, as displayed in FIG. 24C, begins to adjust the robot'sdirection of movement so that the robot will return to a path includedwithin the chosen travel vector 3456. To do this, the cruise controlbehavior alters the robot's heading so that the robot will drive along apath included within a translational vector 3462 calculated to cause therobot 3460 to return to the chosen travel vector 3456. FIG. 24D displaysthe final effect of the translational vector 3462 in that the robot 3458moves from a path included within the avoidance travel vector 3462 to apath within the chosen travel vector 3456.

In an embodiment of the invention, the cruise control behavior assumesthat the robot is moving at a velocity of 0 m/s, and considers therobot's position to be the normal position. Subsequent rotationalvelocities and accelerations/decelerations are an alteration of therobot's 0 m/s velocity and normal position. Alternatively, the cruisecontrol behavior could include cruise routines that allow foracceleration and/or decelerations of a robot with a velocity other than0 m/s. In such an embodiment, an additional actuator may be included onthe operator control unit 20 so that the user can control activation ofcruise control with an actuator separate from the puck.

Other preferable features of the cruise control behavior are fail safeconditions that cause the cruise control behavior to halt. Theseconditions include actuating brakes included within the drive system,utilizing the right puck or the puck not designated to control thecruise control behavior, the depression of a brake button, a change indrive mode, or a drop in communication with the robot 10. Additionally,there is a maximum speed at which the robot can go and the robot isconfigured not to drive at a speed higher than the maximum speed.

The present invention contemplates alternative methods of implementingthe cruise control behavior, for example including setting a point farin the distance and driving towards that point, so that when a behaviorlike obstacle detect interrupts, the cruise behavior can calculate apath from the robotic platform's current position back to the originalcruise path, or calculate a new path from the robotic platform's currentposition to the destination point.

The present invention contemplates control of a wide variety ofautonomous assist behaviors. Other autonomous assist behaviors mayinclude, for example: “circle vehicle” where a vehicle is aligned usingwireframe indicia and the remote vehicle follows an odometry-estimatedsquare around the vehicle, keeping its camera pointed to the estimatedcenter of the square; retrotraverse; go to stow position; go to prairiedog position; go to prairie dog position and pan camera back and forth;scan 360 degrees; and scan 720 degrees.

Exemplary Operational Scenarios

The control system of the present invention is used to control a remotevehicle in a variety of missions. Some exemplary operational scenarios(missions) include abandoned vehicle searches, vehicle checkpointsearches, urban assault—clearing the enemy from a geographical area,building searches, cave/tunnel/sewer clearing, and encampment perimetersecurity.

1. A control system for operation of a remote vehicle, comprising: atwin-grip hand-held controller having a volume of less than 1 liter anda weight of less than 1 lb, the twin-grip hand-held controllerincluding: a left grip shaped to be held between a user's left littlefinger, ring finger, and the ball of the thumb, leaving the user's leftindex finger, middle finger, and thumb free; a left control zoneadjacent to the left grip, including a first analog joystick and a first4-way directional control manipulable by the left thumb, and a leftrocker control located on a shoulder portion of the controller; a righthanded grip shaped to be held between the user's right little finger,ring finger, and the ball of the thumb, leaving the user's left indexfinger, middle finger, and thumb free; a right control zone adjacent theright grip, including a second analog joystick and a second 4-waydirectional control manipulable by the right thumb, and a right rockercontrol located on a shoulder portion of the controller; a tether zonebetween the left control zone and the right control zone, including atether anchor configured to tether the hand controller between the leftgrip and the right grip and to permit the hand controller to hang withthe left grip and right grip pointing upward; a tether extending fromthe tether anchor to the right shoulder of an operator, the tetherincluding a strain relief section; and a quick-release pad to be worn onan operator's chest, the quick-release pad including a first fastenerfor affixing the quick-release pad to available mounts on the operator,and a second quick-release fastener for holding the hand-held controllerto the quick-release pad to be readily removable by pulling on thehand-held controller.
 2. A control system for operation of remotevehicle having a main drive and a flipper drive articulated in a pitchplane, the control system comprising: a processor capable ofcommunicating with the remote vehicle; a twin-grip hand-held controllerfor providing commands to the processor, the twin-grip hand-heldcontroller including: a left grip that permits a user's left indexfinger, left middle finger, and left thumb to operate controls; adriving joystick for forward/reverse and left/right steering of theremote vehicle, and a first array of buttons, the driving joystick andthe first array of buttons being manipulable by the user's left thumb; acamera joystick for controlling a camera pose of the remote vehicle, anda second array of buttons, the camera joystick and the second array ofbuttons being manipulable by the user's right thumb; a rocker controlfor controlling a flipper of the remote vehicle, the rocker controlbeing aligned along a pitch plane parallel to the articulated flipperdrive, and controlling a rotational position of a flipper drive; and abrake control that actuates a brake on the remote vehicle.
 3. Thecontrol system of claim 2, wherein the brake control is adjacent to thedriving joystick and manipulable by the user's left thumb.
 4. Thecontrol system of claim 2, wherein the brake control is a dead man'sswitch located under the user's left forefinger, left middle finger,right forefinger, or right middle finger.
 5. The control system of claim2, wherein one of the first array of buttons and the second array ofbuttons includes a speed governor that sets speed ranges for the remotevehicle.
 6. The control system of claim 2, wherein one of the firstarray of buttons and the second array of buttons selects amongpredetermined poses for the robot.
 7. A control system for operation ofremote vehicle having a main drive and a flipper drive articulated in apitch plane, the control system comprising: a processor capable ofcommunicating with the remote vehicle; a twin-grip hand-held controllerfor providing commands to the processor, the twin-grip hand-heldcontroller including: a left grip that permits a user's left indexfinger, left middle finger, and left thumb to operate controls; adriving joystick for forward/reverse and left/right steering of theremote vehicle, and a first array of buttons, the driving joystick andthe first array of buttons being manipulable by the user's left thumb; acamera joystick for controlling a camera pose of the remote vehicle, anda second array of buttons, the camera joystick and the second array ofbuttons being manipulable by the user's right thumb; and a mode buttonor toggle located under the user's left forefinger, right forefinger,left middle finger, or right middle finger.
 8. A control system foroperation of remote vehicle having a main drive and a flipper drivearticulated in a pitch plane, the control system comprising: a processorcapable of communicating with the remote vehicle; a twin-grip hand-heldcontroller for providing commands to the processor, the twin-griphand-held controller including: a left grip that permits a user's leftindex finger, left middle finger, and left thumb to operate controls; adriving joystick for forward/reverse and left/right steering of theremote vehicle, and a first array of buttons, the driving joystick andthe first array of buttons being manipulable by the user's left thumb; acamera joystick for controlling a camera pose of the remote vehicle, anda second array of buttons, the camera joystick and the second array ofbuttons being manipulable by the user's right thumb; and one of adirectional pad or a right button array for selecting among one or morepredetermined poses of the remote vehicle.
 9. The control system ofclaim 8, wherein the predetermined poses include predefined positions ofthe remote vehicle's flippers and camera.
 10. The control system ofclaim 8, wherein the predetermined poses include predefined positions ofthe remote vehicle's flippers, head and neck.
 11. The control system ofclaim 8, wherein selection of a predetermined poses is made with theuser's right thumb.
 12. The control system of claim 8, furthercomprising a user interface illustrating the predetermined posesavailable for selection.
 13. The control system of claim 12, furthercomprising software for transitioning among the predetermined poses. 14.The control system of claim 13, wherein the software for transitioningamong the predetermined poses transitions the remote vehicle througharbitrary intermediate poses.
 15. The control system of claim 8, furthercomprising means for returning a camera of the remote vehicle to adefault position.
 16. A control system for operation of remote vehiclehaving a main drive and a flipper drive articulated in a pitch plane,the control system comprising: a processor capable of communicating withthe remote vehicle; a twin-grip hand-held controller for providingcommands to the processor, the twin-grip hand-held controller including:a left grip that permits a user's left index finger, left middle finger,and left thumb to operate controls; a driving joystick forforward/reverse and left/right steering of the remote vehicle, and afirst array of buttons, the driving joystick and the first array ofbuttons being manipulable by the user's left thumb; a camera joystickfor controlling a camera pose of the remote vehicle, and a second arrayof buttons, the camera joystick and the second array of buttons beingmanipulable by the user's right thumb; and one of a directional pad or aright button array for selecting among one or more autonomous assistbehaviors of the remote vehicle.
 17. The control of claim 16, whereinthe autonomous assist behaviors include at least one of ballisticbehaviors and continuous behaviors.
 18. The control system of claim 16,wherein the autonomous assist behaviors include predefined positions ofthe remote vehicle's flippers and camera.
 19. The control system ofclaim 16, wherein the autonomous assist behaviors include predefinedpositions of the remote vehicle's flippers, head, and neck.
 20. Thecontrol system of claim 16, wherein selection of an autonomous assistbehavior is made with the user's right thumb.
 21. The control system ofclaim 16, further comprising a user interface illustrating theautonomous assist behaviors available for selection.
 22. The controlsystem of claim 21, further comprising software for controlling theautonomous assist behaviors.